Software Vault: The Diamond Collection

home *** CD-ROM | disk | FTP | other *** search

/ Software Vault: The Diamond Collection / The Diamond Collection (Software Vault)(Digital Impact).ISO / cdr38 / rtp195.zip / SYSOP.DOC < prev next >

Wrap

Text File | 1995-03-08 | 29KB | 553 lines

RISE TO POWER Version 1.95 -- Program & Design by Robert A. Dalton Based on original source code by Chris R. Tynes Copyright (C) 1993 Compiled using SCOTT BAKER's Door Driver Routines (Registered) and Borland Pascal 7.0 (Professional). --> NOTE: Changes in this document file are preceded with an "*" INTRODUCTION: ------------ RISE TO POWER is a on-line door game of intrigue based in 15th Century Germany. The goal is to advance from a land holding Knight to King and unite the 10 provinces of Germany. To do this you will have to use treachery, guile and force of arms. DISCLAIMER: ---------- To the extent of this SysOp's knowledge, this software will cause not damage whatsoever to your system. HOWEVER, no warranty is given or implied. By running this software, you hereby submit to the rules and limitations imposed by the author. NEITHER THE AUTHOR, NOR ANY OF THE TEST SITES, SUPPORT BOARDS, OR ANYONE OF ANY RELATION TO THE GAME MAY BE HELD RESPONSIBLE FOR ANY OF THE VARIOUS POSSIBLE PROBLEMS THAT MAY OCCUR. IF YOU DO NOT AGREE WITH ANY OF THE RULES OR REQUIREMENTS STATED, DO NOT USE THIS PACKAGE! *REQUIREMENTS: ------------ At this point in time the only requirements are FILES=10 (or more) in your config.sys file and ANSI.SYS. SHARE must also be loaded if you are running this on a multi-node system. The game is RIP aware but NOT a RIP Game at this time. A FOSSIL is NOT required to run the game, although one will be supported if it exists and you have configured the CTL file to show one is present. Automatic time slicing support is provided to most common multi-taskers as well. Files Included -------------- Below is a listing of all files for the RISE TO POWER Game. If you are missing ANY of these files (except for the DOC and FRM files), the game will NOT function. Feel free to give out copies of the ENTIRE archive package of RTP but please make sure all the files below are in that package: ASSASSIN.ANS - Assassin ANSI Menu Screen ATTACK.ANS - Attack Player's Keep ANSI Menu Screen BARON.ANS - Baron's Keep ANSI Menu Screen DUEL.ANS - Duel ANSI Screen LOCKED.ANS - Screen shown when another node accesses the game KING.ANS - King's Keep ANSI Menu Screen MAPMENU.ANS - Large Screen ANSI Map Display PLAYER.ANS - Player's Keep ANSI Menu Screen RTOPEN.ANS - ANSI Opening Screen for RISE TO POWER RTP_1.ANS - ANSI Keep with Drawbridge Open RTP_2.ANS - ANSI graphic of Keep with Drawbridge Closed RTP_3.ANS - ANSI graphic of Addition to Keep RTP_6.ANS - ANSI Graphic of constructed church RTP_7.ANS - ANSI Graphic of meeting another player RTP_8.ANS - ANSI Graphic of assassin attacking player from behind RTP_10.ANS - ANSI Graphic of message being delivered RTP_11.ANS - ANSI graphic of player being promoted RTP_12.ANS - ANSI Graphic of King Giving hand of women in marriage RTP_13.ANS - ANSI Graphic of treasure chest RTP_15.ANS - ANSI graphic of meeting brigands RTP_16.ANS - ANSI graphic of a monk RTP_17.ANS - ANSI graphic of a challenge RTP_18.ANS - ANSI graphic - You become King STAT.ANS - ANSI Player Status Screen TREACH.ANS - Treachery ANSI Menu Screen VISIT.ANS - Visiting Players ANSI Menu Screen WMAIN.ANS - RISE TO POWER Main ANSI Menu Screen SAMPLE.BAT - A sample BAT file for Door.sys on a single node system SAMPLE1.BAT - A sample BAT file for door.sys on a multi-node system RTP1.CTL - Un-edited and heavily commented sample of a CTL Control file for setting up RTP and hereafter referred to in the game documentation as GAME.CTL. If you decide to use it, be sure to rename it to RTP.CTL first! SAMPLE.CTL - A copy of the RTP.CTL file which I use on my BBS to run the game (WildCat 4.01S System, 386 33Mhz Computer, Single Node, 8Mb RAM, DesqView 2.63/ QEMM 7.04, BNU Fossil locking port #1 at 19200 and using FrontDoor 2.02 and a US Robotics DS Modem, ANSI.sys loaded and SHARE loaded). I have left the comments in so you can understand what I am doing. KEY.DAT - Dummy Key for RISE TO POWER (Good forever!) LOCKED.DAT - File used for locking out nodes on multi-node system MAPDATA.DAT - ASCII game map for RISE TO POWER-DO NOT ALTER! OLDNEWS.DAT - Yesterdays news FILE_ID.DIZ - ASCII Description File for BBS Sysops on RTP B4UASK.DOC - Checklist to help resolve setup/game problems HISTORY.DOC - RTP Version History information file SYSOP.DOC - This text file you are reading UPGRADE.DOC - If you are upgrading - read this first! MAINT.EXE - Nightly maintenance program for RISE TO POWER DDSETUP.EXE - RTP CTL configuration program. RTP.EXE - RISE TO POWER Main Program RTPEDIT.EXE - RISE TO POWER Game Editor Program RTPINIT.EXE - RISE TO POWER Game Initializing Program REGISTER.FRM - Preprinted registration form and mailer BUGRPT.FRM - Preprinted bug report/suggestion/comment form and mailer CATALOG.TXT - Descriptive catalog of all games available from me. DSITES.TXT - List of sites where my games are distributed. INSTRUCT.TXT - Game Player Instructions for RISE TO POWER RTP.ZIP - Compressed copy of the above instructions to make available on your BBS for download by players of the game. Files created by RISE TO POWER upon initialization: COUNTRY.DAT - Province Information file GEN.DAT - General Information file GLOB.DAT - Global variables Information File MAP.DAT - Map Information File MESSAGE.DAT - Message Storage File NEWS.DAT - News and Player Log Information File PLAYER.DAT - Player Information File Files created by RISE TO POWER when first played: RTPSCORE.DAT - ASCII Scores information Bulletin KILLEM.DAT - Created to store deleted players temporarily. Files that may be created by RISE TO POWER as needed: ERROR.LOG - Created by main program if error occurs MERROR.LOG - Created by maintenance program if error occurs Installation ------------ 1. Create a directory for the game (example: "WC30\DOORS\RTP") 2. Make sure that ALL files listed above from the RTP194.ZIP file are moved into that directory. 3. Type "DDSETUP.EXE" and hit the enter key. The first thing it will ask you is what the name of the CTL file is. Type in "RTP.CTL" and then proceed to the other settings. After you are done the RTP.CTL file should be correctly configured. Two versions of a fully commented CTL file are provided for manual configuration. One is identified by the game title (example: GAME.CTL) and this is the UN-EDITED version and the other is identified as SAMPLE.CTL is what a CTL file should look like AFTER it is edited. If all else fails - try the one I use on MY support BBS (Sample.CTL). If you have fossil drivers be sure to uncomment the 'fossil' option. If you have a modem set to a non-std IRQ be sure to use the PORT# option for that com port. A CTL file generated by DDSETUP.EXE will have NO comments and look quite different from my samples, but they WILL work just as well, never fear. Where to put this file? Put this file wherever you are running the game executable file from. If you are running multi-node you could put a copy in each node directory and run from there. If you change directory to the GAME directory put the file here. See the example SAMPLE#.bat files. 4. Edit the Key.DAT file. Line #1 should be the sysops name, Line #2 should be the name of the using BBS, do NOT change or edit line #3. 5. In order to run the game program online the following parameters may be used. "/Bxxxxx" This tells GAME.EXE to lock its baud rate at xxxxx. In order to get the most efficiency out of a high speed error correcting modem (9600 baud or above), you may lock the baud rate to a speed higher than what the caller is actually using. By locking the baud to say 38,400, the modem can compress text data that is being sent and achieve a baud rate much higher than the actual transmission rate. This will lock the baud rate at the same value for all nodes that use this command line. If you perfer a more selective way to lock baud use 'LOCKBAUD' command in the GAME.CTL file. "/Cx" (where x is 1..4) This specifies a comport number. Some bbs software does not create door information files (dropfiles) that contain the comport number. If your bbs does have a comport listed in the dropfile then there is no need for this parameter. The default is comport 0, local mode. "/E" - Expanded Memory Specification If your machine has over one megabyte of memory, then you may have some available. GAME.EXE can utilize EMS to improve game performance and reduce conventional memory requirements. This command will tell GAME.EXE to use EMS memory to hold its overlay buffer. Otherwise disc area may be used to hold this buffer. This needs a memory manager and when enabled and is compatible with DESQview. "/L" This tells GAME.EXE to load up in LOCAL mode. This is good for testing or when a sysop just wants to "try out" the door without messing with his BBS setup. The "/L" mode will ask the user for his name and run the door in local mode. "/Nx" (where x is 1..9) This specifies a "node number". Some bbs software support multinode environments in which you must know the node number of the drop file to use. For example, RBBS-PC uses DORINFOx.DEF. If you specified "/N2" then GAME.EXE would use DORINFO2.DEF. "/Mx" (where x is up to 2 filename acceptable characters) Used to specify one of Multiple control files. If you have created more than one GAME.CTL file (GAME1.CTL, GAME2.CTL, etc.) for each node or network PC then you can select the one you want by using the /M parm. Example: "/M2" will force GAME.EXE to use GAME2.ctl. "/Pyyy" This specifies the path to the drop files. For example, "/PC:\WILDCAT\WCWORK\NODE1" would tell GAME.EXE to look for the drop file in C:\WILDCAT\WCWORK\NODE1. If this is left out the program assumes the drop file is local. "/V" This command will tell GAME.EXE not to show any display on the local screen. Only a colored screen and a message will be displayed. The cursor will not move as it will be turned off. Saves a little processing on multi-tasking systems. "/W" This flags the program that a network is present even though no multitaskers are detected. This is useful if the door is run on a network such as Novell that doesn't use multitaskers. COMMON ERRORS 003 File path not found. Check to make sure the game directory is correctly named as GAMEDIR. 201 Files not found. Check to make sure that all required games files are in the GAMEDIR directory. 6. Install the door into your BBS software (see your BBS software documentation for more information). A batch file is normally used to do this. To run the program just have your batch file change to the GAMEDIR directory and run GAME.EXE - Thats all there is to it! Three different batch files sample are included to help you run the game. These are included with the game for editing and your use. Remember when writing the batch routines for my games you must ensure that the game is run from it's home directory AND that the game knows where to find the drop file. Satisfy these two requirements and you should have no problems running the game as long as the other setup criteria has been met. For dorinfo systems try using the following: Sample Batch File ----------------- COPY DORINFOx.DEF \RBBS\DOORS\GAMEDIR\*.* CD \RBBS\DOORS\GAMEDIR GAME x <-=- NODE number !!DO NOT USE "x"!! del dorinfox.def CD \WC30 --> Please note that you replace the "x" with the appropriate node number. Ex: Dorinfo1.def ; Dorinfo2.def ; etc... 7. Run RTPINIT.EXE to initialize the game and create required game data files. This file automatically initializes the game with default values. If you are a REGISTERED user and want to run a custom game use the RTPEDIT.EXE program instead of the RTPINIT.EXE program. The RTPEDIT program will NOT function unless you are registered. 8. Manually run MAINT.EXE to initialize quests and other required game information. Thereafter make sure your BBS Software runs the MAINT.EXE program on a daily basis as an event. One note on maintenance: Players will be automatically deleted after 10 days of inactivity. 9. If you would like a score bulletin just have the game batch file copy the RTPSCORE.DAT file to wherever you have your bulletins. Example: Copy C:\WC30\DOORS\RTP\RTPSCORE.DAT C:\WC30\BULL\BULL11.BBS 10. If you would like the news file to become a bulletin just have the game batch file copy the NEWS.DAT file to wherever you have your bulletins. Example: Copy C:\WC30\DOORS\RTP\NEWS.DAT C:\WC30\BULL\BULL12.BBS RESTRICTIONS ON THE UNREGISTERED GAME ------------------------------------- Until the game is registered the following restrictions are in effect: a. Game time is limited to less then 10 minutes per player. b. The Game editor (RTPEDIT.EXE) cannot be used. c. The game is limited to 10 players. d. There will be a slight delay experienced by players at the beginning of the game. WHAT TO DO IF THERE ARE PROBLEMS -------------------------------- Every effort is made to ensure that the game runs correctly before it leaves my BBS as Shareware. If you are experiencing problems please do the following BEFORE calling me: 1. Read ALL the SYSOP.DOC to ensure you have setup the program and have met all the program requirements. 2. Use the B4UASK.DOC as a checklist to ensure that you have not done anything wrong. *Multinode use ------------- RTP WILL run on a multi-node system but only one node can play the game at anyone time. If a second node tries to play the game they will be presented with the LOCKED.ANS screen and after a short delay returned to the BBS. I realize this is not the BEST solution to allow these game to be utilized on multi-node systems but it is the best one for NOW. Sometime before 1995 I intend to convert the game to FULL multi-node and give it the capability to to be used by several players at ONCE. Until then this is the best I can do to help all you "multi-noders" out. Common Problems (Locked Bauds, High Speed modems, etc) ------------------------------------------------------ 1. The game does NOT require a fossil driver to run. 2. If you are running a high speed modem (9600 baud or above), then I suggest you run your bbs/mailer/doors at a locked baud rate. On high speed error correcting modems, locking the baud rate will have a noticeable increase on the speed of text that is sent. It's beyond the scope of this document to discuss configuring your BBS and mailer for a locked baud rate; you may wish to consult those docs for information on that. Here are a few things to keep in mind when setting up GAME with a locked baud rate: a. When using a locked baud rate, I highly recommend using a FOSSIL driver. This game will work at high speeds without one though. BNU is a good fossil driver which can even be loaded and unloaded before and after you run this game. b. If you are using a fossil, then make sure to tell the fossil that the port is locked. For BNU, to lock com1: at 38,400, you would use something like "L0=38400" on BNU's command line. c. If you lock the baud for one program, it must be locked for everything. You can't lock the baud for just this game, but not your BBS/mailer. d. You may need to use the /B switch on the game.exe Command line to specify the locked baud rate. For 19,200 this would be "/B19200" and for 38,400 this would be "/B38400". Please note there is no space between the "/B" and the baud rate. 3. What follows is some information on possible strange situations that may occur: a. Low speed users can play the game, but high speed users get garbage. - If you are not using the DORINFOx.DEF or DOOR.SYS drop file then you may wish to find a converter program to convert whatever drop file your BBS produces to the DORINFOx.DEF or DOOR.SYS format and tell game.exe to use that. Several converter programs are readily available on most BBS systems. CallDoor is a good one if you can find it. I have it on my BBS for download if you need it. b. The game hangs up when a user enters the game. - Sounds like the game is getting the wrong baud rate somehow. Try switching over to the DOOR.SYS drop file method if possible. c. Text and screens are getting cut off. - If you are running with a locked baud, then this could be caused by some sort of FLOW CONTROL problem. Try using a fossil if you aren't already. d. If you're using something other than the DOOR.SYS drop file, then I always suggest trying to use DOOR.SYS if possible. It is the most reliable method and has had the most testing. If that is not possible try DORINFOx.DEF as an alternative. e. A door locks up node 1. This can happen with fossils or the internal communications routines because it uses the default comport of 1 when NONE is found in the dropfile or game.ctl file. To correct this make sure the right port is shown in the dropfile OR game.ctl file. f. ANSI is reflected correctly on the local screen but the user is getting garbage. Assuming the user has ANSI installed then most likely the problem is at your end. First make sure you have configured the game.ctl file to show the correct locked port rate. Second make sure the dropfile is passing the locked port rate INSTEAD of the actual conncet rate. If it is not passing the locked port rate then you may need to use a different dropfile format OR use a dropfile converter program to change the line to show the locked port rate INSTEAD of the actual connect rate. Restarting the Game ------------------- 1. Run RTPINIT.EXE to initialize the new game files. If the old ones are still in the directory, don't worry, the program will simply overwrite them. It is not necessary to delete any files before running the RTPINIT.EXE program. If you are a REGISTERED user and want to run a custom game use the RTPEDIT.EXE program instead of the RTPINIT.EXE program. The RTPEDIT program will NOT function unless you are registered. 2. Run MAINT.EXE to setup the first quest. 3. That's it! "Corrupted" data files ---------------------- It is possible that something could happen to your RTP data files. A power outage, RTP crash, or other event could damage one of the data files. If you get one of these messages, then the best thing to do is start the game over with a clean copy of RTP. CREDITS: This relatively small section is just to recognize the GOOD people who have made this door a possibility. Chris R. Tynes -=*=- The original author of the source code on which this game is based and who very graciously allowed me to use it to make this game. Michael Arnett -=*=- For his generous donation of the custom ANSI art opening screen in this game. Violet Stymacks -=*=- For her generous donation of the custom ANSI art in this game. Scott Baker -=*=- The author of the door driver package which made this game possible. Great job Scott!! Steven Lorenz -=*=- The author of the enhanced add on package to Scott Bakers DoorDriver. Thanks to his allowing me to use his modifications I was able to delete the fossil requirement and add many new communication enhancements to the latest version of RTP. Thanks Steve! Steve Smith -=*=- Sysop of the Broken Wings BBS for beta testing this version on his BBS and making many recommendations on bug fixes. Charles Halsey, Marjorie Scofield, Adam Grandon, Hal Borland, Titus Campbell, and many others for play testing the game on the TANSTAFL BBS - Thanks guys! Where to reach me ----------------- I can usually be reached at my BBS system, which should be listed in the section entitled "registration" which is below. I also habitually monitor ALL door related echos in the FIDO Net System. Registration ------------ If you or your users enjoy this game, then please register it. Information on price and how to register is shown on the enclosed REGISTER.FRM. Registration will disable the delay, allow additional options and entitle you to life time support through my BBS. BBS Support includes unlimited free updates and upgrades (not like some door game authors who charge for major upgrades/updates!) through my BBS and access to the game support conference on my BBS. To register this game just print out the registration form (REGISTER.FRM) file included with the game and send it with your check or money order to: Robert A. Dalton 203 Old Farm Road Harrison, AR 72601 HOW TO REACH ME BY MODEM --------------------------- The TANSTAFL BBS (USA) (501) 741-5699 (USR Dual- 2400 to 14400 baud) Fidonet 1:391/3010 Reminder: You will be mailed a LETTER with your registration code. Just allow an appropriate amount of time (a week or two) after dropping your check in the mail for it to arrive to me and the code to be sent by mail back to you. If you need it sooner log onto my BBS, leave me a message telling me you mailed the registration and when I receive your check or money order I will post a private message on the BBS giving you the key code. If you do it this way please allow at least a week from the time you mail it to the time you call and get your code. If you go the BBS route you will ALSO receive a key code by mail. If you live in NORTH AMERICA I can also send your key via Netmail for an additional $1.00, if you would like, through the FIDO system (only). REMINDER: No disks are sent, if you need the most current version you must call OR freq my BBS for it. Bug Reports/Comments/Suggestions -------------------------------- I have made every attempt to make sure the game is free of bugs, BUT the possibility always exists that one may have been missed by me or the playtesters. If you find a bug, or have a suggestion or comment to make which would make future versions better please print out the BUGRPT.FRM and mailer, fill it out, and send it to me. I read ALL of them and those people that lead me to find a bug or generate a better game will receive credit in the game documentation. PLEASE DO NOT NOTIFY ME OF PROBLEMS AND EXPECT ME TO FIX THEM IF YOU HAVE FAILED TO PROVIDE ME WITH THE BUGRPT.FRM AND OTHER INFORMATION I REQUIRE AS STATED IN THE B4UASK.DOC. FIDO INFORMATION ---------------- My BBS supports file "freq"ing at 9600 baud or above. Just call 1:391/3010. I also carry a door library of over 350 of the all time best door games which I try to keep current. For a list of these doors just freq "DOORS". I am always adding new things to my games so most likely there will be a later version of the program available on my BBS then the one you have. For a current version of the game just freq the magic name shown in the catalog document which is in the game package. For a list of ALL my files just freq "TANSTAFL.ZIP". If you are a door game/program writer why not send me a copy of your game/program? If you have a more current version of a door then I have, please consider sending me a copy as a token of your appreciation for the service I offer at NO cost to you. Thanks!